Bugzilla

At the moment it appears we are only getting ASan logs from content process crashes and not parent process crashes on Windows.

The best/only way I've found to repro this is using FFPuppet (automatically setup the env and profile). This method works (we get ASan logs as expected) on Linux and MacOS.

This can obviously be done with out FFPuppet but I can't get Firefox to dump logs to the file system consistently otherwise :(

STR:
1) Install [FFPuppet](https://github.com/MozillaSecurity/ffpuppet) and get an ASan build
2) Launch the browser `python -m ffpuppet -d <path_to_firefox>`
3) Navigate to `about:crashparent`

Expected results:
- An ASan log should be present in the output

Actual results:
- **Windows 10 1909:** No ASan logs are present.
- **Linux & MacOS:** ASan logs are present.

Bonus points:
To make this even more exciting opening `about:crashcontent` on Windows only provides output after navigating to a page.
to summarize... 
- `about:crashcontent` in newtab -> no output
- `about:crashcontent` after navigating to page -> asan log
- `about:crashparent` -> no output ever!

At the moment it appears we are only getting ASan logs from content process crashes and not parent process crashes on Windows.

The simplest way I've found to reproduce this is using FFPuppet (automatically setup the env and profile). This method works (we get ASan logs as expected) on Linux and MacOS.

This can obviously be done with out FFPuppet but I can't get Firefox to dump logs to the file system consistently otherwise :(

STR:
1) Install [FFPuppet](https://github.com/MozillaSecurity/ffpuppet) and get an ASan build
2) Launch the browser `python -m ffpuppet -d <path_to_firefox>`
3) Navigate to `about:crashparent`

Expected results:
- An ASan log should be present in the output

Actual results:
- **Windows 10 1909:** No ASan logs are present.
- **Linux & MacOS:** ASan logs are present.

Bonus points:
To make this even more exciting opening `about:crashcontent` on Windows only provides output after navigating to a page.
to summarize... 
- `about:crashcontent` in newtab -> no output
- `about:crashcontent` after navigating to page -> asan log
- `about:crashparent` -> no output ever!

At the moment it appears we are only getting ASan logs from content process crashes and not parent process crashes on Windows.

The simplest way I've found to reproduce this is using FFPuppet (automatically setup the env and profile). This method works (we get ASan logs as expected) on Linux and MacOS.

This can obviously be done without using FFPuppet but I can't get Firefox to dump logs to the file system consistently otherwise :(

STR:
1) Install [FFPuppet](https://github.com/MozillaSecurity/ffpuppet) and get an ASan build
2) Launch the browser `python -m ffpuppet -d <path_to_firefox>`
3) Navigate to `about:crashparent`

Expected results:
- An ASan log should be present in the output

Actual results:
- **Windows 10 1909:** No ASan logs are present.
- **Linux & MacOS:** ASan logs are present.

Bonus points:
To make this even more exciting opening `about:crashcontent` on Windows only provides output after navigating to a page.
to summarize... 
- `about:crashcontent` in newtab -> no output
- `about:crashcontent` after navigating to page -> asan log
- `about:crashparent` -> no output ever!